Conversation
| ```yaml | ||
| cds: | ||
| ai.chat.models: | ||
| llm: |
There was a problem hiding this comment.
| llm: | |
| default: |
| | `options` | Additional provider-specific parameters. | | ||
|
|
||
| An agent picks its model configuration via the `@agent.llm` annotation, which defaults to | ||
| the configuration named `llm`. If no configuration matches, CAP Java falls back to `aicore` |
There was a problem hiding this comment.
| the configuration named `llm`. If no configuration matches, CAP Java falls back to `aicore` | |
| the configuration named `default`. If no configuration matches, CAP Java falls back to `aicore` |
There was a problem hiding this comment.
Will the annotation look like @agent.llm: "myllmconfig" then? @agent.llm is the static annotation name and "myllmconfig" is the key in application.yaml? if the annotation is missing, it will use the "default" key.
There was a problem hiding this comment.
Yes, but the default key is (currently) called llm
There was a problem hiding this comment.
Ok. I thought based on your comment that this was changed to default. @agent.llm: 'llm' is harder to understand than @agent.llm: 'default'. I think this is nothing we can change now, right?
There was a problem hiding this comment.
I also would prefer default here; it's currently llm to be in sync with the Node runtime, they use cds.requires.llm for the config.
| ```yaml | ||
| cds: | ||
| ai.chat.models: | ||
| llm: |
There was a problem hiding this comment.
| llm: | |
| default: |
| ```yaml | ||
| cds: | ||
| ai.chat.models: | ||
| llm: |
There was a problem hiding this comment.
| llm: | |
| default: |
| An agent turns a CDS service into a conversational endpoint. It answers natural-language | ||
| requests by using the service's entities, actions, and functions as tools, backed by an | ||
| LLM. Agents speak the [A2A protocol](https://a2a-protocol.org/), so any A2A-compatible | ||
| client can talk to them. |
There was a problem hiding this comment.
We should spend a word on the supported a2a protocol version. As Agent Gateway only support version 0.3, we decided to support by default only 0.3. We have an (undocumented) property which allows to activate 1.0.
There was a problem hiding this comment.
@StefanHenke, @beckermarc feel free to add
| | `options` | Additional provider-specific parameters. | | ||
|
|
||
| An agent picks its model configuration via the `@agent.llm` annotation, which defaults to | ||
| the configuration named `llm`. If no configuration matches, CAP Java falls back to `aicore` |
There was a problem hiding this comment.
Will the annotation look like @agent.llm: "myllmconfig" then? @agent.llm is the static annotation name and "myllmconfig" is the key in application.yaml? if the annotation is missing, it will use the "default" key.
|
|
||
| ### SAP AI Core | ||
|
|
||
| With an `aicore` service binding, requests run through |
There was a problem hiding this comment.
Does aicore offer different service plans which might be relevant here?
3 participants
No description provided.